[uss_qualifier/scenarios] Improve documentation for SCD0030 test#1369
Merged
BenjaminPelletier merged 1 commit intointeruss:mainfrom Feb 27, 2026
Merged
Conversation
barroco
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some users have had some confusion regarding this test scenario recently. This PR attempts to clarify its documentation to better describe what modification in the presence of conflict means and the implications of succeeding or not. A hidden assumption about not conflicting with Flight 2m ("whatever is the outcome of this step, there should not be any impact on the rest of the execution of the scenario") is documented, and a few other touch-ups are made.